Where a note in the margin becomes the work.
Write the doc, leave a note, let an agent pick it up. In Margin the thinking and the doing stay on the same page.
Free for up to 10 people. No card needed.
Margin HQ
- Q3 launch brief
- Support playbook
- Hiring loop
- Design review notes
- Weekly sync
Q3 launch brief
We ship the margin rail on the 14th. Everything below is what has to be true by then — write straight into it, and leave a note wherever you want help.
Before we ship
- Rewrite the pricing page headline Wren
- Ship the margin rail to staging Dara
- Changelog entry for 2.4 Agent
- Security review sign-off Priya
Pricing lands with the release, so the sign-off has to come before Friday
Release agent
WorkingI picked up Dara’s note. The 2.4 changelog is drafted from the three merged PRs and it reads clean. Publish it?
Reading: Q3 launch brief
Written in every day at
Everything the team knows, on one page.
Margin holds the writing, the work and the conversation about both — so the answer is never three tools away.
One place the whole team actually writes in.
Docs, projects, decisions and the notes hanging off them. Nothing lives in four tools and three inboxes any more.
See how docs work- #launch in Slack
- 12 PRs in GitHub
- Q3 roadmap in Linear
- Support tickets
Q3 launch brief
Everything that has to be true before the 14th, and who owns it.
Answers that show their working.
Ask in plain language. Margin answers from your own pages and hands you the line it read.
See searchwhy did we move pricing to usage?
Because seats punished the teams inviting the most people. Usage tracks the value they actually get.
Pricing rewrite · line 14
Every note, waiting on one board.
A note in the margin becomes a card the moment somebody needs it done. Nothing gets typed twice.
See projectsTo do
- Rewrite pricing headline
- Security review
Doing
- Ship the margin rail
- Draft the 2.4 changelog
Done
- Migrate the old notes
Work carries on without you in the room.
An agent reads the note, reads the page it sits on, and does the part that never needed a person. It shows every step, so you are approving work rather than trusting a black box.
How agents workDraft the 2.4 changelog from these PRs.
Dara · in Q3 launch brief
Release agent
- Read the note and the page it sits on
- Pulled the three PRs merged since 2.3
- Drafted the entry in the house voice
- Waiting on Dara to publish
Margin 2.4 — the margin rail arrives. Notes now attach to any block, agents can pick them up, and the changelog you are reading wrote itself.
Six things you stop doing yourself.
Not features. The specific jobs a team hands over in the first fortnight.
-
Triage the inbox
Every message read, sorted and answered where the answer is already written down.
-
Write the changelog
From the pull requests that actually shipped, in the voice the last ten entries used.
-
Keep the docs honest
Flags the page that contradicts the one you just changed, before a customer finds it.
-
Answer the same question
The eleventh time somebody asks where the runbook is, it answers instead of you.
-
Chase the sign-off
Knows who owns the decision, asks them once, and closes the note when they reply.
-
Summarise the week
One page on Friday: what moved, what slipped, and the note nobody picked up.
Teams that write things down.
-
We stopped writing the same decision down in three places. That is the whole pitch, and it turned out to be worth a headcount.
Rowan Ellery
Head of Operations
-
The margin notes are the thing. Our reviews used to end in a doc nobody opened again — now they end in work that has an owner.
Sasha Merrin
Director of Product Design
-
Our agents draft the changelog, the release notes and half the support replies. We read them. That is a fair trade.
Ari Vance
Engineering Lead
- 38,000
- teams write here every day
- 4.1M
- notes picked up by an agent
- 62%
- of the Fortune 100 use Margin
- 11 min
- median time from note to done
Start on the page you are already writing.
Free for up to ten people, and your first agent runs on day one.